The windows cygwin failure is odd, I actually tested the package on my turtle vm and it succeeded. Let's wait on #28833 to be merged, I'll update the topkg constraint and we'll get a better error message.

For the rest we just have a problem with alpine that I need to investigate. It seems the getentropy C call is not defined. I guess it's a musl thing to look into.

I merged the other PR

Aaah it's nice to see the actual errors in the opam error snippet :–) So many years and it took a cmd.exe limitation to improve topkg's error reporting.

So we have this:

'D:\opamroot\default\lib\ocamlbuild/ocamlbuild.cmx' -o myocamlbuild.exe
  # + ocamlfind ocamlc -config
  # + pkg-config --libs-only-l zlib > 'C:\Users\RUNNER~1\AppData\Local\Temp\pkgconfig3205e2pkg-config'
  # Can't open perl script "/cygdrive/c/Strawberry/perl/bin/pkg-config": No such file or directory
  # Command exited with code 2.

I'd say the error is weird but indeed the build system expects and runs pkg-config even if you don't configure any bytesrw depopt. Yet there is no dependency of the package towards conf-pkg-config. Let's try to add it.

The error persists (but our dependencies are more correct). I posit however that this is not an error with bytesrw but with the install of conf-pkg-config on Windows cygwin ?

 # + ocamlfind ocamlc -config
  # + pkg-config --libs-only-l zlib > 'C:\Users\RUNNER~1\AppData\Local\Temp\pkgconfig2dfc08pkg-config'
  # Can't open perl script "/cygdrive/c/Strawberry/perl/bin/pkg-config": No such file or directory
  # Command exited with code 2.

So I'd suggest to merge this. Alpine has been constrained away, the alpine support will be restored with a bugfix release.

The vif revdep failure is because the package seems to be doing tests I suspect it should not perform on the opam CI /cc @dinosaure or @hannesm.

You can merge this PR regardless vif which is on beta.

You can merge this PR regardless vif which is on beta.

That's not the point :–) I think you should disable these kind of tests for the opam repository. It's annoying both for repo maintainers and submitters to have to sift through these errors.

If vif test cannot run, we should indeed disable them here on the repository

Thanks both!

Thanks @mseri. Any idea about what to do about this pkg-config issue on windows ?

Unfortunately not. I have zero experience on windows, and only access to windows in the ci here. I would wait for some windows user to help us out if they hit the issue :P

I would wait for some windows user to help us out if they hit the issue :P

I'm not sure they will. I did not. I thought perhaps there is something wrong with the CI itself.

Every now and then it happens. But indeed it may well be a CI issue, especially if nobody ever reports it